-
Notifications
You must be signed in to change notification settings - Fork 274
Migrate from vercel to sites blog #2496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Added a blog post detailing seven reasons to migrate from Vercel to Appwrite Sites, highlighting benefits such as improved developer experience, cost efficiency, and full cloud platform integration.
WalkthroughAdds a new static blog post page at src/routes/blog/post/migrate-from-vercel-to-appwrite-sites/+page.markdoc. The file includes front matter fields (layout, title, description, date, cover, timeToRead, author, category, featured, callToAction) and full markdown content outlining seven reasons to migrate from Vercel to Appwrite Sites: git push workflow parity, full Next.js support, global CDN via multi-CDN, scalable cost structure, broader cloud platform integration, open-source/self-hosting, and a low-disruption migration path. Includes a wrap-up and linked resources. No changes to exported/public entities. Suggested reviewers
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/routes/blog/post/migrate-from-vercel-to-appwrite-sites/+page.markdoc (1)
67-70
: Standardize internal link format.Line 70 uses an absolute URL (
https://appwrite.io/...
) while the other resource links (lines 68-69) use relative paths. For consistency and to avoid potential routing issues, all internal links should use the same format.Apply this diff to standardize the link format:
# More resources - [Appwrite Sites documentation](/products/sites) - [Announcing Appwrite Sites: The open source Vercel alternative](/blog/post/announcing-appwrite-sites) -- [Appwrite Sites vs Vercel: Choosing the right web hosting platform](https://appwrite.io/blog/post/open-source-vercel-alternative) +- [Appwrite Sites vs Vercel: Choosing the right web hosting platform](/blog/post/open-source-vercel-alternative)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/routes/blog/post/migrate-from-vercel-to-appwrite-sites/+page.markdoc
(1 hunks)
🔇 Additional comments (2)
src/routes/blog/post/migrate-from-vercel-to-appwrite-sites/+page.markdoc (2)
1-70
: LGTM! Well-structured blog post.The blog post is well-written with clear structure, compelling arguments, and appropriate marketing tone. The content effectively communicates the benefits of migrating from Vercel to Appwrite Sites. The front matter is properly formatted, and the markdown content is well-organized with logical flow from introduction through seven key reasons to the conclusion.
19-19
: Verify documentation links and feature claims.The blog post references several Appwrite features and documentation pages:
- Line 19:
/docs/products/sites/deployments
and/docs/products/sites/previews
- Line 31:
/docs/products/network/cdn
- Lines 45-46:
/docs/products/functions
,/docs/products/databases
,/docs/products/auth
- Line 53:
/docs/advanced/self-hosting
- Line 57:
/docs/products/sites/migrations/vercel
Please ensure these documentation pages exist and the feature descriptions are accurate.
Run the following script to verify the documentation links:
Also applies to: 31-31, 45-46, 53-53, 57-57
What does this PR do?
(Provide a description of what this PR does.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)
Summary by CodeRabbit